Repository navigation
Change Naming Convention - Block/Allow Listing for Clarity and Inclusion - #19571
Conversation
* For clarity and better inclusion
| JavaScript no es seguro). | ||
|
|
||
| ### [¿Por qué utilizar una lista blanca de sitios que admiten HTTPS? ¿Por qué no pueden intentar utilizar HTTPS para cada sitio, y sólo volver a HTTP si no está disponible?](#why-use-a-whitelist-of-sites-that-support-https-why-cant-you-try-to-use-https-for-every-last-site-and-only-fall-back-to-http-if-it-isnt-available) | ||
| ### [¿Por qué utilizar una lista blanca de sitios que admiten HTTPS? ¿Por qué no pueden intentar utilizar HTTPS para cada sitio, y sólo volver a HTTP si no está disponible?](#why-use-a-allowlist-of-sites-that-support-https-why-cant-you-try-to-use-https-for-every-last-site-and-only-fall-back-to-http-if-it-isnt-available) |
There was a problem hiding this comment.
"lista blanca" still translates as "white list" literally.
There was a problem hiding this comment.
This is true, I am working internally to get a proper translation of this term since Spanish is a secondary language for me personally.
There was a problem hiding this comment.
¿Por qué utilizar una lista de sitios aprobados que admiten HTTPS?
|
@zoracon I understand why make this change in user-facing parts, but is the use of this term still problematic if it is not user-facing (like file names)? I can imagine Also, entire |
cschanaj
left a comment
There was a problem hiding this comment.
Inclusive and descriptive terminologies are great for open source projects. I believe it would be awesome if we could take the opportunities to improve our documentation as well. Just one thing that is not strictly functional, and could be fixed possibly later.
Thank you for the work 👍
| * [Will there be a version of HTTPS Everywhere for IE, Safari, or some other | ||
| browser?](#will-there-be-a-version-of-https-everywhere-for-ie-safari-or-some-other-browser) | ||
| * [Why use a whitelist of sites that support HTTPS? Why can't you try to use | ||
| * [Why use a allowlist of sites that support HTTPS? Why can't you try to use |
There was a problem hiding this comment.
I find this question in the FAQ is misleading on how HTTPS Everywhere works. It is also inconsistent with the terminology we use. I believe this question would be better rephrased to avoid confusion.
HTTPS Everywhere use a collection of peer-reviewed rulesets to upgrade insecure HTTP connections to HTTPS. We also use the terminology "Add a rule for this site" on the extension user interface, our users "Enable"/ "Disable" rules with checkbox as needed.
Would something like Why use bundled rulesets to upgrade insecure connections to HTTPS? better?
P.S. I am not a native English speaker, so please forgive me if I am asking a weird question.
There was a problem hiding this comment.
I would suggest "Why not just redirect all websites by default?" "Why not redirect every possible website?". The simplest wording possible is often the best one.
There was a problem hiding this comment.
I can change the wording, just have to coordinate a small effort to get the translation. I can schedule that into the next round of documentation updates. Wanted to focus on this renaming portion first. I will note this in the documentation items that need to be done.
Thank you both so much for reviewing with great care and compassion.
@pipboy96 Any code or files that is user facing or not, other developers out there like you all will see it. Which is enough reason for me to change it to something more inclusive. I was contemplating removing this directory ( |
|
Tagging in @andresbase for Spanish translation for "Allow List" |
| @@ -15,7 +15,7 @@ recursos [enumerados aquí](https://www.eff.org/https-everywhere/development). | |||
| * [¿Por qué utilizar una lista blanca de sitios que admiten HTTPS? ¿Por qué | |||
There was a problem hiding this comment.
[¿Por qué utilizar una lista de sitios aprobados que admiten HTTPS? ¿Por qué
|
Allow List = Lista de Sitios Aprobado |
Co-authored by @andresbase
…everywhere into refactor/renaming-listing
Note: If there's any functional problems that occur from this renaming, please feel free to comment. However, this is not a debate forum for allowlist vs. blocklist
Open Source Community Examples: